home *** CD-ROM | disk | FTP | other *** search
/ Developer Source 9 / developer source - volume 9.iso / ieees / may97 / tartt01b.gif < prev   
Graphics Interchange Format  |  1998-02-10  |  78KB  |  548x483  |  4-bit (13 colors)
Labels: text | screenshot | font | number | black and white | document
OCR: TABLE 1B PROPOSED CLASSIFICATION: FINE-GRAINED CRITERIA Criterion and Definition Classes and Examples Comments Granularity (G): The size and structure Line (I): version control. Page (p). c.mmp page This criterion extends the selectivity criterion. of the coherence data object marking, one-time identifiers. Segment (s): condi- It is irrelevant for fully indiscriminate schemes. tional invalidation. Flexible (f): RP3 flexible inval- idation, adaptive cache management. Blocking (B): The basic program block as Critical region (c): one-time identifiers, condi- The epoch class encompasses terms such as a code unit for coherence protocol tional invalidation. Epoch (e): Ultracomputer "computational unit," "loop," "epoch," and program structure analysis, cache on/off control, "task level," which are essentially similar program analysis and reference marking, version coherence blocks. control, timestamps. Subroutine (s): program- mable cache. Program (p): c.mmp page marking. Positioning (P): Position of instructions Entry/exit of critical region (e): one-time identi- This criterion considers only the special to implement the coherence protocol fiers, conditional invalidation. Loop boundary (b): coherence instructions (Invalidate, Flush cache on/off control, version control. Source/sink Post, and so on). It does not include coherence of data dependency (d): programmable cache. actions such as comparisons at cach reference, Interrupt procedure (i): coherence on which some schemes can do with special hard- interrupt request. ware support. Updating (U). The main memory is up- Write-through (t) version control. Write-back (b); Hybrid schemes typically offer both write- dated either during the write or later programmable cache, adaptive cache management. through for shared writeable data and write-back Hybrid (h): one-time identifiers. Alternative (a): for private and shared read-only data. Alternative conditional invalidation. schemes offer either write-through or write-back. Checking (C): Technique used to check Checking data type or reference type (r): c.mmp Some schemes include multiple techniques for conditions of incoherence page marking, program analysis and reference detecting incoherence. Such schemes are classi- marking, timestamps. Program structure ana- fied according to the dominant technique. For lysis (s): RP3 flexible invalidation, cache on/off completeness, we indicate the lesser techniques control. Data dependency analysis: (d): program- with slashes, for example c/+sed+r/. mable cache. Bitwise information runtime comparison (b): fast selective invalidation, life- spain strategy, one-hit timestamps. Version com- parison (v): version control. Generation com- parison (g): generational approach. Monitoring interconnection network traffic (m): coherence on interrupt request.